The RichText component was creating label and Sprite nodes that did not propagate the Sorting2D component that the RichText had. This resulted in incorrect render orders for rich text because all it's child nodes would render on the default layer with 0 sorting order.

This pull request fixes this issue: #19015

Example project archive:
richtextbadlayer_example.zip

Example of issue:
layer setup:

Before fix:

After fix:

Re: #

Changelog

• Added Sorting2D components on label and image nodes of the richText node if the richText has a Sorting2d component on it. Updated their values with the ones from the richText node

Continuous Integration

This pull request:

• needs automatic test cases check.

  Manual trigger with @cocos-robot run test cases afterward.

• does not change any runtime related code or build configuration

  If any reviewer thinks the CI checks are needed, please uncheck this option, then close and reopen the issue.

Compatibility Check

This pull request:

• changes public API, and have ensured backward compatibility with deprecated features.
• affects platform compatibility, e.g. system version, browser version, platform sdk version, platform toolchain, language version, hardware compatibility etc.
• affects file structure of the build package or build configuration which requires user project upgrade.
• introduces breaking changes, please list all changes, affected features and the scope of violation.

Greptile Summary

• Fixes RichText rendering order issue where child Label and Sprite nodes did not inherit Sorting2D properties from parent RichText components, causing incorrect layer ordering
• Implements iOS-specific WebGL VAO invalidation fixes to handle buffer update synchronization issues in Safari's WebGL-to-Metal translation layer
• Adds version tracking system for buffers and VAOs with hash-based staleness detection to prevent rendering corruption on iOS devices

Important Files Changed

Confidence score: 4/5

• This PR addresses well-documented issues with solid implementation patterns but involves complex graphics pipeline changes that require careful testing
• Score reflects the iOS VAO fixes being platform-specific workarounds for WebGL-to-Metal translation issues, plus the RichText change affecting UI component hierarchies
• Pay close attention to WebGL command files which implement intricate buffer versioning logic and VAO recreation mechanisms that could impact rendering performance

Sequence Diagram

sequenceDiagram
    participant User
    participant WebGL2CmdFuncUpdateBuffer
    participant Device
    participant GL as "WebGL Context"
    participant VAO as "VAO Cache"
    participant IA as "Input Assembler"

    User->>WebGL2CmdFuncUpdateBuffer: "Update buffer data"
    WebGL2CmdFuncUpdateBuffer->>Device: "Check if iOS"
    alt iOS Platform
        WebGL2CmdFuncUpdateBuffer->>WebGL2CmdFuncUpdateBuffer: "Increment updateVersion++"
        WebGL2CmdFuncUpdateBuffer->>VAO: "Unbind current VAO"
        WebGL2CmdFuncUpdateBuffer->>GL: "gl.bindVertexArray(null)"
        WebGL2CmdFuncUpdateBuffer->>IA: "Invalidate input assembler cache"
    end
    WebGL2CmdFuncUpdateBuffer->>GL: "Bind target buffer"
    WebGL2CmdFuncUpdateBuffer->>GL: "gl.bufferSubData() or gl.bufferData()"
    
    Note over User,IA: Later during rendering...
    
    User->>WebGL2CmdFuncBindStates: "Bind rendering states"
    WebGL2CmdFuncBindStates->>Device: "Check if iOS and VAO needed"
    alt iOS Platform and VAO Required
        WebGL2CmdFuncBindStates->>WebGL2CmdFuncBindStates: "Compute current buffer versions"
        WebGL2CmdFuncBindStates->>VAO: "Check cached VAO version"
        alt Version Mismatch
            WebGL2CmdFuncBindStates->>GL: "Delete old VAO"
            WebGL2CmdFuncBindStates->>GL: "Create new VAO"
            WebGL2CmdFuncBindStates->>VAO: "Store new version hash"
        end
    end
    WebGL2CmdFuncBindStates->>GL: "Bind VAO for rendering"